-
Notifications
You must be signed in to change notification settings - Fork 87
New routine to traverse all nodes of a JSON structure. #144
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Current coverage is
|
Current coverage is
|
Looks good to me. One comment: would you mind changing the output so only json_print (and other stuff that creates valid JSON structures) is writing to stdout, and anything informational or relating to status, warning and error messages is written to stderr? This is the convention for most/all of the other tests, with the goal being to eventually validate their outputs with jsonlint in the CI test suite. The only thing, as far as I remember, that is preventing this is a few tests output multiple valid JSON objects which the linter we were using flagged as problematic. |
end if | ||
|
||
if (error_cnt==0) then | ||
write(output_unit,'(A)') '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’d prefer everything other than json_print
to write to stderr so that one day I can finish implementing the output validation with a JSON linter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's fine. Will do that later today.
New routine to traverse all nodes of a JSON structure. Fixes #140
See #140